Skip to content

Mark every route as a requirement of a declared class or an extension - #85

Merged
estebanzimanyi merged 1 commit into
masterfrom
test/ats-routes-are-classes-or-extensions
Nov 19, 2026
Merged

estebanzimanyi merged 1 commit into
masterfrom
test/ats-routes-are-classes-or-extensions

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

routeTable holds every operation the service serves: its method and path,
its handler, and the conformance class it is a requirement of, or extension
for a MobilityAPI extension. newMux routes by it, and the API definition marks
each operation by it, with x-conformance-class naming the class or
x-mobilityapi-extension. The class URIs the conformance declaration lists are
constants the table, the declaration and the tests read.

ats_routes_test.go holds the three to each other: a route marked with a class
the conformance declaration does not list, a route the API definition does
not describe, an operation it describes that no route serves, and a route an
abstract test of Annex A issues that is marked as an extension or with
another class, each fail. Of the 45 routes, 33 are requirements of a declared
class (Common core 3, mf-collection 5, movingfeatures 14, cquery 5, Coverages
core 2, EDR core 4) and 12 are extensions: /health, trajectories, timeseries,
export, bulk, PUT of a moving feature, the live ingest of a temporal property
and the five routes of the geometry continuous query.

Witness. GET /health, /collections/{cid}/trajectories and
/collections/{cid}/timeseries were served and absent from the API
definition, since the routing table and the API definition were two lists.

Measured. go test passes; renaming /health in the API definition fails the
test from both sides, the served route undescribed and the described one
unserved. samples/api-definition.json is what the service writes, emitted as
samples.go writes it; the same emission over master reproduces master's
sample byte for byte.

routeTable holds every operation the service serves: its method and path,
its handler, and the conformance class it is a requirement of, or extension
for a MobilityAPI extension. newMux routes by it, and the API definition marks
each operation by it, with x-conformance-class naming the class or
x-mobilityapi-extension. The class URIs the conformance declaration lists are
constants the table, the declaration and the tests read.

ats_routes_test.go holds the three to each other: a route marked with a class
the conformance declaration does not list, a route the API definition does
not describe, an operation it describes that no route serves, and a route an
abstract test of Annex A issues that is marked as an extension or with
another class, each fail. Of the 45 routes, 33 are requirements of a declared
class (Common core 3, mf-collection 5, movingfeatures 14, cquery 5, Coverages
core 2, EDR core 4) and 12 are extensions: /health, trajectories, timeseries,
export, bulk, PUT of a moving feature, the live ingest of a temporal property
and the five routes of the geometry continuous query.

Witness. GET /health, /collections/{cid}/trajectories and
/collections/{cid}/timeseries were served and absent from the API
definition, since the routing table and the API definition were two lists.

Measured. go test passes; renaming /health in the API definition fails the
test from both sides, the served route undescribed and the described one
unserved. samples/api-definition.json is what the service writes, emitted as
samples.go writes it; the same emission over master reproduces master's
sample byte for byte.
@estebanzimanyi
estebanzimanyi merged commit 6af707a into master Nov 19, 2026
2 checks passed
@estebanzimanyi
estebanzimanyi deleted the test/ats-routes-are-classes-or-extensions branch November 19, 2026 09:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant